Skip to content

fix: remove node from exports map #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 28, 2025
Merged

fix: remove node from exports map #126

merged 1 commit into from
Jul 28, 2025

Conversation

kyletsang
Copy link
Collaborator

Don't think the node field in exports map is required anymore since this now supports proper ESM. This is causing an issue in RB when consuming from an ESM perspective since types are resolving to the CJS variant.

@kyletsang kyletsang requested a review from jquense June 25, 2025 04:55
@@ -3,6 +3,8 @@
"compilerOptions": {
"jsx": "react-jsx",
"lib": ["DOM", "ESNext"],
"moduleResolution": "bundler",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes errors when viewing test files in the IDE since this isn't needed for vitest

@apepper
Copy link

apepper commented Jul 11, 2025

@jquense A review would be highly appreciated. AFAICS this PR currently blocks the attempt to get react-boostrap version 3 with React 19 support out (see react-bootstrap/react-bootstrap#6939).

@reteps
Copy link

reteps commented Jul 25, 2025

@jquense bump!

@kyletsang
Copy link
Collaborator Author

This is a very minor change and we can fix stuff in a follow-up PR if needed. It does fix the type resolution issue in RB, so let's see what else appears in the next beta

@kyletsang kyletsang merged commit 6113f4b into main Jul 28, 2025
15 of 21 checks passed
@kyletsang kyletsang deleted the remove-exports-node branch July 28, 2025 06:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants